Skip to content

Port Foswiki appliance to TurnKey 19 - #9

Open
lirazsiri wants to merge 3 commits into
masterfrom
fix/foswiki-v19-upgrade-evidence
Open

Port Foswiki appliance to TurnKey 19#9
lirazsiri wants to merge 3 commits into
masterfrom
fix/foswiki-v19-upgrade-evidence

Conversation

@lirazsiri

Copy link
Copy Markdown
Member

Summary

  • port Foswiki to Debian Trixie with firstboot administrator provisioning
  • update appliance configuration, scheduled work, and supported package plan
  • add focused v19 acceptance including a digest-verified Foswiki 2.1.10 to 2.1.11 upgrade

Validation

  • independent re-review: SHIP at 54ee965
  • exact PASS run 20260826t043024z-5565-11697
  • retained manifest verified, including preserved administrator authentication and topic content after upgrade
  • git diff --check origin/master...54ee965

Move the appliance to Debian 13 and the maintained Foswiki 2.1.11 security release. Pin and verify the official release digest, and generate LocalSite.cfg from the current upstream schema so stale configuration does not block the build.

Preserve web-server ownership of the firstboot password file, restore documented scheduled maintenance, and add focused acceptance coverage for administrator login, CSRF-protected topic persistence, inherited services, and the supported update channel.

Verified in a disposable Trixie environment with the real configure and firstboot paths, Apache HTTPS, administrator authentication, topic create/read persistence, and all three maintenance commands. Static shell, Python, and diff checks also pass.
The v19 build generated a current Foswiki configuration, but that process did not create the password-manager file expected by the firstboot hook. Normal initialization therefore failed before administrator authentication.

Install the Debian htpasswd utility explicitly, create the documented admin account from the firstboot password over standard input, and set the password file to the ownership and mode required by the web service. Static shell and Python validation pass; the exact appliance build and login flow remain the acceptance gate.
Replace release-discovery-only updater evidence with a disposable 2.1.10 to 2.1.11 upgrade using Foswiki's published procedure. Verify both official archive digests and reuse the real administrator login and topic flow to prove state survives the upgrade.

Open the root-private verified archive in the test shell so Foswiki's documented extraction still runs as the web server user.

Verification: bash -n tests/v19.sh; git diff --check; focused private-archive extraction as www-data in tkldev19-dev. Exact run 20260826t042014z-8079-4475 passed build, firstboot, and runtime readiness, then reproduced the corrected archive permission failure.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant